Skip to content

Conversation

@tsipinakis
Copy link

Why? A picture is a thousand words:

2025-08-20T18-32-43 2025-08-20T18-32-17

@tsipinakis
Copy link
Author

I fixed the possible undefined errors during build, note that this is the first time I ever touch TS and Vue, so let me know if there are more standard ways to do what I did 😅

@tsipinakis
Copy link
Author

Ready for another lint run/review

Copy link
Contributor

@stvncode stvncode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the great enhancement! Just some small comments on non-null assertion

@OzGav
Copy link
Contributor

OzGav commented Sep 20, 2025

Having just started to play with Audiobooks there are a number of considerations here. For audiobooks with not so many chapters having the full timeline means you can click on the chapter mark to jump to that chapter. Obviously in the example above this is not that relevant as there are so many chapters so maybe not something to worry about. However, while on this subject one thing the UI lacks is an indication of which chapter is currently playing. Is there anything we can do there?

P.S. Check the lint probs...

@tsipinakis
Copy link
Author

Whoops indeed I pushed to the wrong branch again, pushed to the one I use for my own build, but forgot to also push to the MR one 🙈

However, while on this subject one thing the UI lacks is an indication of which chapter is currently playing. Is there anything we can do there?

Indeed, though out of scope for this MR, maybe next one :)

@marcelveldt
Copy link
Member

Without showing the user that this is a chapter playing, this is going to cause unclarity. We need to figure out the UX how to display/select chapters. Silently only showing the current chapter makes the progress bar nicer maybe not perse more easier.

@tsipinakis
Copy link
Author

Silently only showing the current chapter makes the progress bar nicer maybe not perse more easier.

At least for me, now it takes it from completely unusable and dangerous (misclick means I lose my place and jump to a random place in the book), to useful as I can seek around.

I agree about the indication though - but I'd say this can be a first step to be merged as it's an opt-in and users should be aware that they have switched it on.

I do intend to look at the second part after.

@OzGav
Copy link
Contributor

OzGav commented Oct 8, 2025

You can just touch a chapter in the list to jump there

@tsipinakis
Copy link
Author

I just added audiobook chapter subtitles, this should be better now.

@OzGav
Copy link
Contributor

OzGav commented Oct 15, 2025

Have you got some screenshots?

@tsipinakis
Copy link
Author

2025-10-15T14-29-19 2025-10-15T14-29-29

const tempTime = ref(0);
const chapterTime = computed(() =>
localStorage.getItem("frontend.settings.audiobook_chapter_time") == "true"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we certain a computed property is the right way to do this ?
Like, will it only be computed once and not over and over ?

Copy link
Author

@tsipinakis tsipinakis Oct 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, have not used vue before this. I'm open to ideas.

On the other hand: Does it matter? How much overhead is a map lookup?

@OzGav
Copy link
Contributor

OzGav commented Oct 16, 2025

@marcelveldt This subtitle idea is somewhat aligned with the concept of providing another line in the now playing view to provide extra information for the Radio Paradise provider? Should we review that for a consolidated approach?

@tsipinakis
Copy link
Author

@marcelveldt Ready for another review round

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants